This page shows FAQs of Monitoring.
When you click the question, the answer will be displayed.
A bar in gray appears in the graph on Monitoring GUI. What is this?
A bar in gray in the graph on Monitoring GUI shows the day of week on weekend. Note that date in the graph on Monitoring GUI is shown in order of “day.month”.
Is the output result of AWS-compatible API or parameter which must be specified different from AWS?
Yes, a little. For more details, refer to the “Cloudn Monitoring Operational Manual” and “API Manual”.
Time stamp is shown in the return value of API. What is the time zone of this time stamp?
Time stamp may be shown in the output result depending on API type.
Because Cloudn Monitoring is released only in Japan, the time zone of time stamp is JST. We will support other time zone notation in future.
I cannot obtain the metrics value a several minutes after resources monitored are created.
In Cloudn Monitoring, it takes about 30 minutes to start monitoring and obtain the metrics value after the resources are created. Please wait a while.
Is the CPU usage rate from the virtual server different from the CPU usage rate obtained by CPU Utilization metrics of Cloudn Monitoring?
The CPU usage rate from guest OS on the virtual server is different from the CPU usage rate from the hypervisor obtained by Cloudn Monitoring.
The CPU usage rate from the hypervisor is calculated considering the CPU ration allocated to the virtual server. Cloudn Monitoring obtains that value.
How long is the metrics data saved?
Monitoring metrics data of Cloudn Monitoring is saved for two weeks. You can refer to it from GUI or API.
Is there any limit for the number of alarms which can be created?
We don’t limit the number of alarms which can be created in Cloudn Monitoring currently but we may limit the number in future depending on the load situation in the entire system from now.
An error returns when I try to set the start point of horizontal axis in the graph to “50 minutes ago” in Time Range of Cloudn Monitoring GUI.
You cannot set the start / end points of horizontal axis in the graph to the value of 1 hour or less in Time Range now. Set the value to more than 1 hour in the graph.
I specify the StartDate and EndDate parameters in DescribeAlarmHistory API but they are not reflected to the return values.
We don’t support the StartDate and EndDate parameters in DescribeAlarmHistory API now. We are very sorry.
I add the data disk simultaneously when creating a virtual server but I cannot obtain the metrics on the DataDisk well.
Root disks and data disks of virtual server created by Cloudn Compute can be monitored by DataDisk metrics of Cloudn Compute.
However when the root disks and data disks are created simultaneously (when creating the data disk in the virtual server creating wizard, etc.), you may not be able to obtain the metrics value successfully in rare cases.
We will correct this case in the recent days. If you want to monitor the root disk and data disk of virtual server at the moment, create the virtual server, create the data disk and then attach it.
When an abnormality occurs on the virtual server of Cloudn Compute or Compute system, you can use StatusCheckFailed to detect it.
Currently Compute metrics (StatusCheckFailed, StatusCheckFailed_Instance andStatusCheckFailed_System) monitor followings:
・StatusCheckFailed_Instance： The virtual server (VM) does not stop on the hypervisor.
・StatusCheckFailed_System: The VM management mechanism of hypervisor operates correctly.
・StatusCheckFailed： Normal when the two above metrics are normal.
The hypervisor is monitored by the cloud platform system (CloudStack) and tries to continue the virtual server operation in the event of failure.
For example, when the hardware of physical server on which the virtual server is running fails, the cloud platform system automatically moves the said virtual server onto other normally-running hypervisor. Therefore you may not be able to detect the failure at the above metrics monitoring timing.
As the cloud platform system deletes the virtual server stopped from the hypervisor VM list, the virtual server may not be sent as monitoring metrics.
When the abnormality is detected with the above metrics, you may not obtain the value representing the abnormality currently and metrics are not updated (the last update time is in past). We will correct this case in the recent days in order that these metrics can reflect the VM operation status appropriately. Please wait for a while.